Skip to content

feat(website): ✨ read the versions and their dates from npm - #75

Merged
diecodev merged 1 commit into
ci/website-deployfrom
feat/website-npm-versions
Oct 29, 2026
Merged

diecodev merged 1 commit into
ci/website-deployfrom
feat/website-npm-versions

Conversation

@diecodev

Copy link
Copy Markdown
Owner

The website had the versions written by hand: @beta in the menu and
the install commands, 2.0.0-beta.0 in the header, the changelog and the
structured data, while the release came out as 2.0.0-beta.1. Each
release, and 2.0 going stable, meant editing them.

The site now reads npm when it builds (vite.config.ts defines what
src/data/npm.ts reads: the dist-tags and the day of each version), and
src/data/release.ts names each major from it: its dist-tag while only
prereleases are out (@beta, @rc), @2 once stable, installed as
plain qwik-date when latest is the newest major. The version menu,
the install command and its "keep @beta" note, the compatibility table,
the link from the 1.x docs and the version in the structured data
follow; the changelog's sections take their newest version, its tag
and its day (or "unreleased"), and list the ones before. Offline, a
local build shows the repo's version as unreleased; in the CI it fails
instead.

llms.txt and llms-full.txt come from templates too (scripts/llms.md and
llms-full.md, written by scripts/llms.ts, which pnpm build.website now
runs first), so they leave the repo.


Stack created with GitHub Stacks CLI • Give Feedback 💬

The website had the versions written by hand: `@beta` in the menu and
the install commands, 2.0.0-beta.0 in the header, the changelog and the
structured data, while the release came out as 2.0.0-beta.1. Each
release, and 2.0 going stable, meant editing them.

The site now reads npm when it builds (vite.config.ts defines what
src/data/npm.ts reads: the dist-tags and the day of each version), and
src/data/release.ts names each major from it: its dist-tag while only
prereleases are out (`@beta`, `@rc`), `@2` once stable, installed as
plain `qwik-date` when `latest` is the newest major. The version menu,
the install command and its "keep @beta" note, the compatibility table,
the link from the 1.x docs and the version in the structured data
follow; the changelog's sections take their newest version, its tag
and its day (or "unreleased"), and list the ones before. Offline, a
local build shows the repo's version as unreleased; in the CI it fails
instead.

llms.txt and llms-full.txt come from templates too (scripts/llms.md and
llms-full.md, written by scripts/llms.ts, which `pnpm build.website` now
runs first), so they leave the repo.
@vercel

vercel Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
qwik-date Ready Ready Preview Oct 29, 2026 5:16pm UTC

@diecodev
diecodev added this pull request to stack #77 October 29, 2026 17:15
@diecodev
diecodev merged commit 6eae9d2 into main Oct 29, 2026
5 checks passed
@diecodev
diecodev deleted the feat/website-npm-versions branch October 29, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant